-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Microsoft.Logic - Don't make ResourceReference id readonly #4491
Microsoft.Logic - Don't make ResourceReference id readonly #4491
Conversation
…DK where an Logic Apps with integration accounts can't be saved
If you're a MSFT employee, click this link |
Can one of the admins verify this patch? |
Automation for azure-sdk-for-pythonThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-jsThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-rubyThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-nodeThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-goNothing to generate for azure-sdk-for-go |
Automation for azure-sdk-for-javaA PR has been created for you based on this PR content. Once this PR will be merged, content will be added to your service PR: |
…4491) * Add Clusterpool readonly GET field for AKS agentpool MSI resource ID * Fix spacing in property name * Add to 2021 09 15 api version * Add subid and agentpool to custom words
Don't make ResourceReference id readonly, it's causing a bug in the SDK where an Logic Apps with integration accounts can't be saved
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Contribution checklist: